← Back to issue list

snapcraft-managed lxd containers do not respect parallel installs

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1985409
Type
issue
State
open
Author
~alexclewontin
Labels
Created
2022-08-11 18:05:47.381450+00:00
Updated
2022-08-11 18:08:40.280406+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

In the case when multiple instances of snapcraft are installed in parallel (https://snapcraft.io/docs/parallel-installs) instances suffixed with an instance key (e.g. _foo) appear to install the unsuffixed instance from the host into their managed lxd container. This then results in build failure. Steps to reproduce: 1) enable parallel installs as described here: https://snapcraft.io/docs/parallel-installs 2) run `snap install snapcraft --channel=6.x/stable --classic` (revision 7201 at reporting time) 3) run `snap install snapcraft_7 --channel=7.x/stable --classic` (revision 8093 at reporting time) 4) initialize a fresh snap using `snapcraft init` and change the base to core22 5) try to run `snapcraft_7` to build that snap $ snapcraft_7 Launching instance... Usage: snapcraft pack [OPTIONS] DIRECTORY Try 'snapcraft pack -h' for help. Error: No such option: --build-for Failed to execute pack in instance. Full execution log: '/home/alex/.cache/snapcraft/log/snapcraft-20220811-135653.968445.log' Execution log attached to bug report Lines of interest: 63, 66 I have not tested this using other permutations of versions across parallel installs, or using multipass

Evaluation history

No evaluation history available.